Systems and Methods for Internal Initialization of a Nonvolatile Memory

ABSTRACT

Methods and systems are provided that may include a memory device having a physical nonvolatile memory, a memory space, and a controller. At least a portion of a physical nonvolatile memory may permit a direct read operation of the physical nonvolatile memory and prohibit a direct write operation of the physical nonvolatile memory. A memory space may comprise at least open one write overlay window available after a reset operation. Such a memory space may be adapted to permit at least one read overlay window to be opened that is logically separate from at least one open write overlay window. A controller may be included to open at least one read overlay window.

CROSS-REFERENCE TO RELATED APPLICATION

This application is a continuation application of U.S. application Ser.No. 12/347,962, filed Dec. 31, 2008, the entirety of which isincorporated by reference herein.

BACKGROUND

1. Field

The subject matter disclosed herein relates to a nonvolatile memory.

2. Information

Nonvolatile memory devices, such as Phase-Change Memory (“PCM”), flashmemory, or Electrically Erasable Programmable Read-Only Memory(“EEPROM”) are sometimes packaged within an electrical system. Forexample, such nonvolatile memory devices may be sold within a computersystem or a digital camera, for example. Such nonvolatile memory devicesmay be coupled to a bus and data may be transmitted over such a bus froma processor to a nonvolatile memory device for storage, for example.

Information such as data or program code may be transmitted over a busto a nonvolatile memory, where it may be written for storage. Similarly,information may be read, or retrieved, from a nonvolatile memory andtransmitted over a bus to an electronic component such as a processor.

BRIEF DESCRIPTION OF THE DRAWINGS

Non-limiting and non-exhaustive aspects are described with reference tothe following figures, wherein like reference numerals refer to likeparts throughout the various figures unless otherwise specified.

FIG. 1 illustrates a nonvolatile memory device according to oneimplementation.

FIG. 2 illustrates an electronic system according to one implementation.

FIG. 3 illustrates a non-volatile memory device having two separateoverlay window types, a read overlay window and a write overlay window,according to one implementation.

FIG. 4 illustrates a process for implementing read and write overlaywindows according to one implementation.

DETAILED DESCRIPTION

In the following detailed description, numerous specific details are setforth to provide a thorough understanding of claimed subject matter.However, it will be understood by those skilled in the art that claimedsubject matter may be practiced without these specific details. In otherinstances, well-known methods, procedures, components and/or circuitshave not been described in detail so as not to obscure the claimedsubject matter.

Nonvolatile memory devices, such as Phase-Change Memory (“PCM”), flashmemory, or Electrically Erasable Programmable Read-Only Memory(“EEPROM”) devices are sometimes packaged within an electrical system.For example, such nonvolatile memory devices may be utilized within acomputer system or in an electronic device such as a digital camera orpersonal digital assistant (PDA), for example. Such nonvolatile memorydevices may be coupled to a bus and data may be transmitted over such abus from a processor or other electronic component to such nonvolatilememory devices for storage.

In one implementation, some nonvolatile memory devices may not allowdata received via a bus, for example, to be written directly to aphysical nonvolatile memory. Instead, data may be written indirectly toa nonvolatile memory device—for example, data may be written to a memorybuffer. A controller or processor within such a nonvolatile memorydevice may subsequently transfer such data from such a memory buffer tosuch a physical nonvolatile memory.

Data, for example, may be written to a memory buffer of a temporarymemory device, such as static random access memory (SRAM) within anonvolatile memory device, and may be subsequently moved into underlyingphysical nonvolatile memory. It may be faster to write information toSRAM than it would be to write to such information directly to aphysical nonvolatile memory. SRAM may be likewise used to store datarequired by a non-volatile memory device that uses a write overlaywindow as a command interface.

If data is moved across a bus to a nonvolatile memory device, forexample, certain protocols may be followed. If data for a writeoperation were sent directly to a nonvolatile memory device, such datamay not be written to such a nonvolatile memory device. In currentsystems, if a write request is transmitted over a bus from a processoror other system electronic component to a nonvolatile memory, nothingwill be written to such a nonvolatile memory unless an overlay windowhas been opened prior to such a write operation being transmitted to thenonvolatile memory device. A reason for this is because nonvolatilememory devices in current use do not permit direct write operations. Incurrent systems, an overlay window containing a memory buffer is bydefault closed and must be opened within the nonvolatile memory device;only then can such data received from a bus be written to such a memorybuffer of a nonvolatile memory device.

In one implementation, a nonvolatile memory device may use a singleoverlay window which can handle write operations to a memory buffer,direct reads, and status and command interfaces.

According to one implementation, as discussed herein, a number ofseparate overlay window(s) may be utilized for one or more writeoperations versus overlay window(s) used for one or more readoperations. A “write operation” may refer to a physical bus transactionof the type “write.” A “read operation,” on the other hand, may refer toa physical bus transaction of the type “read.” Accordingly, the samecommand, but with different “types,” may be utilized for a read or awrite operation. An implementation, as discussed herein, may provide amethod and system for reading from and writing to a nonvolatilememory-specific memory device Command and Status interface independentof the nonvolatile memory device's physical interface standard. Forexample, in some current systems, a protocol-specific command associatedwith a physical interface may have to be provided to a nonvolatilememory device in order to cause the nonvolatile memory device to open anoverlay window. In such current systems, read operations and writeoperations may be performed within the same overlay window. Accordingly,in the event that, for example, command response information stored in aregister is to be read, an entire overlay window may be opened.Moreover, if information is to be written to a memory buffer, the sameoverlay window would need to be opened.

In one implementation where a nonvolatile memory sits behind a standardmemory bus, such as a Low Power Double Data Rate Nonvolatile Memory(LPDDR-NVM) bus, in order to instruct a nonvolatile memory device toopen an overlay window, a processor may send an LPDDR-NVMprotocol-specific instruction over a bus to a nonvolatile memory device.This protocol may not be found in a standard bus interface specificationbut may instead be defined specifically for a nonvolatile memory'soperation. For example, in the event that the bus is an LPDDR-NVM bus, adifferent instruction may be transmitted than would be transmitted if adouble data rate (DDR) bus, or if a bus according to a differentprotocol were used. A problem may arise because a bus may be specifiedby a standards body, and a manufacturer of a nonvolatile memory devicemay have to request such a standards body to create a protocol-specificcommand to cause such a nonvolatile memory device to open an overlaywindow. A problem with using such protocol-specific commands is that astandards body may have to be petitioned in order to create such aprotocol-specific command.

According to one particular implementation, a nonvolatile memory devicemay include at least one overlay window specifically data inbound to thenonvolatile device or write overlay window. Such a nonvolatile memorydevice may also include at least one overlay window specifically fordata outbound from the nonvolatile device or read overlay window. Suchwrite and read overlay windows may overlap in terms of physical addresslocation, but may, however, be treated as separate portals. In otherwords, at least one write overlay window does not share any physicalregisters or space in memory with at least one read overlay window.Accordingly, at least one write overlay window may therefore belogically separate from at least one read overlay window. If anonvolatile memory device does not support direct write operations tothe underlying nonvolatile memory core, one or more write overlaywindows may remain permanently opened in such a nonvolatile memorydevice. In the event that a write command is received by a nonvolatilememory device, information for such a write command may be written toone or more write overlay windows without a nonvolatile memory devicehaving to first explicitly open a write overlay window.

If a nonvolatile memory supports direct write operations, a nonvolatilememory-specific command may close an underlying write overlay windowprior to such a direct write capability being made available. A devicemay start with all write overlay windows initially open prior to beclosed by one or more nonvolatile specific commands to a write overlaywindow to close the overlay window(s) and enable direct write operationsto an underlying physical nonvolatile memory if that capability isavailable.

Because a write overlay window does not have to be explicitly openedprior to a write operation, there may therefore be no requirement that aprotocol-specific command be created to open such an overlay window. Inorder to subsequently open a read overlay window, for example, certaininformation may be written to a write overlay window. For example,information may be written to a particular register of a write overlaywindow and writing to such a register may cause an internal controlleror processor of a nonvolatile memory device to subsequently perform aprocess to open a read overlay window.

FIG. 1 illustrates a nonvolatile memory device 100 according to oneimplementation. As shown, nonvolatile memory device 100 may includeseveral elements, such as a physical nonvolatile memory 105, a temporarymemory 110, and a controller 115. Nonvolatile memory device 100 maycomprise, for example, a flash memory, Phase-Change Memory (“PCM”), orElectrically Erasable Programmable Read-Only Memory (“EEPROM”).

Physical nonvolatile memory 105 may comprise cells to which information,such as data or program code, for example, may be stored. Temporarymemory 110 may comprise a temporary memory device such as, for example,a static random access memory (SRAM). Temporary memory 110 may comprisea memory buffer 120. A memory buffer 120 may include a memory space inwhich one or more read overlay windows and/or write overlay windows maybe presented.

Controller 115 may be adapted to perform certain functions withinnonvolatile memory device 100 such as, for example, opening at least oneread overlay window. Moreover, controller 115 may also have anotherfunction of moving at least some information stored in temporary memory110 over to physical nonvolatile memory 105. Although controller 115 isshown in FIG. 1, it should be appreciated that controller 115 mayperform a range of processes such that controller 115 may also bereferred to as a processor.

FIG. 2 illustrates an electronic system 200 according to oneimplementation. Electronic system may include a processor 205, a bus210, and a nonvolatile memory device 215. Processor 205 may be adaptedto generate a read command to read data or other information fromnonvolatile memory device 215, and to generate a write command to writedata or other information to nonvolatile memory device 215. Processor205 may transmit a read and/or write command across bus 210 tononvolatile memory device 215. As discussed herein, nonvolatile memorydevice 215 may permit a direct read operation, such that information maybe read directly from a physical nonvolatile memory by an electronicdevice external to nonvolatile memory device 215, such as processor 205in this example. Nonvolatile memory device 215 may also prohibit adirect write operation, whereby information may not be written directlyto a physical nonvolatile memory by an electronic device external tononvolatile memory 215, such as processor 205.

Nonvolatile memory device 215 may include both a physical nonvolatilememory and a temporary memory, such as those discussed above withrespect to FIG. 1. When a write command is received, information may bewritten to a write overlay window within a buffer of a temporary memory,as discussed below with respect to FIG. 3.

FIG. 3 illustrates a memory space 300 for a non-volatile memory devicehaving two separate overlay window types, a read overlay window and awrite overlay window, according to one implementation. Each overlaywindow type may be logically separate but may reside in the same memoryspace according to one implementation. Memory space 300 may include readoverlay window registers 305 and write overlay window registers 310. Inread overlay window space 305, for example, at least one read overlaywindow 315 may be present. In this example, read overlay window 315 mayprovide access to Command Response Data, Command Status, Device Status,or any outbound data that may be registered and accessed via the readoverlay window. Such status information may indicate, for example,information associated with various particulars of a nonvolatile memory,whether certain commands have been executed, how RAM is partitioned, andwhether errors have occurred, for example.

In the example shown in FIG. 3, information may be read directly from aread overlay window 315 or from a physical nonvolatile memory 320.Physical nonvolatile memory 320 may be adapted to store program code,for example, among other types of information. Information can be readdirectly from physical nonvolatile memory 320 if a read overlay window315 is not already open. In the event that a read overlay window 315 isopen, such a read overlay window 315 may be closed to allow informationto be read from physical nonvolatile memory 320. On the other hand, ifinformation is to be read from a read overlay window 315, such a readoverlay window 315 would need to remain open during execution of a readprocess.

The write overlay window registers 310 may be accessed via one or moreof the open write overlay windows 325. An initial state of devicenonvolatile memory device at reset is such that the entire memory spacemay be tiled with open write overlay windows. It is only by subsequentnonvolatile memory commands to an open write overlay window that selectwrite overlay windows may be closed in order to leave only certaindesired overlay window location open. A process, as discussed herein,may be related to initialization of a nonvolatile memory device. Each ofthe write overlay windows 325 may be utilized to store informationreceived from an external device, such as processor 205 of FIG. 2. Theremay be multiple write overlay windows. Use of multiple overlay windowsafter initialization during a boot process may be a choice of anonvolatile memory device. “Host,” as used herein, may refer to a masterdevice that issues commands or accesses a non-volatile memory'scapabilities. A write overlay window 325 may also include a commandinterface and/or a program buffer.

In one implementation, one or more write overlay windows 325 may remainopen because a direct write to underlying physical nonvolatile memory isnot permitted. On the other hand, one or more read overlay windows mayor may not be open at a particular time, e.g., in order to allow readaccess to an underlying physical nonvolatile memory, because a directread from underlying physical nonvolatile memory is permitted. Multipleread overlay windows may be valuable if there are multiple virtualmasters using a non-volatile memory each with their own memory spacepartitioned. In order to open a read overlay window, a write overlaywindow command or protocol may need to be issued or followed, which maycause an internal controller or processor in such a nonvolatile memorydevice to open one or more read overlay windows.

FIG. 4 illustrates a process for implementing read and write overlaywindows according to one implementation. First, at operation 400, atleast one write overlay window is maintained in a memory space of amemory device comprising at least the memory space and a nonvolatilememory. At least a portion of the nonvolatile memory may permit a directread operation while prohibiting a direct write operation. Next, atoperation 405, at least one read overlay window is opened. At least oneread overlay window may be logically separate from the at least onewrite overlay window. At operation 410, at least one read overlay windowregister may be accessed.

In accordance with FIG. 4, it should be appreciated that a nonvolatilememory device may have an ability to keep at least one write overlaywindow in its default open state from all tiled write overlay windows.Only a single read overlay window may ever need to be opened forcommunicating via a command issued to a write overlay window.

Such a method and system, as discussed herein, may provide flexibilityfor manufacturers and users of nonvolatile memory devices. Specifically,such nonvolatile memory devices may be utilized in a variety of systemsand information may be written to or read from such nonvolatile memorydevices without having to utilize protocol-specific commands to open awrite overlay window. Moreover, by segregating a write overlay windowfrom a read overlay window, a permanently-opened write overlay windowmay be utilized.

Some portions of the detailed description which follow are presented interms of algorithms and/or symbolic representations of operations ondata bits or binary digital signals stored within a computing systemmemory, such as a computer memory. These algorithmic descriptions and/orrepresentations are the techniques used by those of ordinary skill inthe data processing arts to convey the substance of their work to othersskilled in the art. An algorithm is here, and generally, considered tobe a self-consistent sequence of operations and/or similar processingleading to a desired result. The operations and/or processing involvephysical manipulations of physical quantities. Typically, although notnecessarily, these quantities may take the form of electrical and/ormagnetic signals capable of being stored, transferred, combined,compared and/or otherwise manipulated. It has proven convenient attimes, principally for reasons of common usage, to refer to thesesignals as bits, data, values, elements, symbols, characters, terms,numbers, numerals and/or the like. It should be understood, however,that all of these and similar terms are to be associated with theappropriate physical quantities and are merely convenient labels. Unlessspecifically stated otherwise, as apparent from the followingdiscussion, it is appreciated that throughout this specificationdiscussions utilizing terms such as “processing”, “computing”,“calculating”, “associating”, “identifying”, “determining” and/or thelike refer to the actions and/or processes of a computing platform, suchas a computer or a similar electronic computing device, that manipulatesand/or transforms data represented as physical electronic and/ormagnetic quantities within the computing platform's memories, registers,and/or other information storage, transmission, and/or display devices.

While certain exemplary techniques have been described and shown hereinusing various methods and systems, it should be understood by thoseskilled in the art that various other modifications may be made, andequivalents may be substituted, without departing from claimed subjectmatter. Additionally, many modifications may be made to adapt aparticular situation to the teachings of claimed subject matter withoutdeparting from the central concept described herein. Therefore, it isintended that claimed subject matter not be limited to the particularexamples disclosed, but that such claimed subject matter may alsoinclude all implementations falling within the scope of the appendedclaims, and equivalents thereof.

What is claimed is:
 1. An apparatus comprising: a nonvolatile memorydevice comprising: a physical nonvolatile memory; and a controller incommunication with the physical nonvolatile memory, wherein uponinitialization, the controller is configured to open at least one writeoverlay window for an address space of the physical nonvolatile memorysuch that the at least one write overlay window implements a status andcommand interface for a host.
 2. The apparatus of claim 1, wherein thecontroller is configured to receive one or more commands via the atleast one write overlay window.
 3. The apparatus of claim 1, wherein thecontroller is configured to open all write overlay windows uponinitialization.
 4. The apparatus of claim 3, wherein the controller isconfigured to close one or more write overlay windows in response to acommand received via the at least one write overlay window.
 5. Theapparatus of claim 1: wherein for a first address space within anaddress space of the physical nonvolatile memory, the controller isfurther configured to permit a direct read operation from the physicalnonvolatile memory and to open a second write overlay window for a writeoperation upon initialization; and wherein for a second address spacewithin the address space of the physical nonvolatile memory, the secondaddress space being different from the first address space, thecontroller is further configured to open a first read overlay window fora read operation and to open a third write overlay window for a writeoperation upon initialization.
 6. The apparatus of claim 1, furthercomprising a temporary memory in communication with the controller. 7.The apparatus of claim 6, wherein the temporary memory comprises astatic random access memory (SRAM).
 8. The apparatus of claim 7, whereinthe controller is configured to receive information in an open writeoverlay window, store the information in the temporary memory, and writethe information to the physical nonvolatile memory.
 9. The apparatus ofclaim 1, wherein the controller is further configured to open at leastone read overlay window upon initialization, wherein the at least oneread overlay window is configured to provide at least command responsedata.
 10. A method of configuring a nonvolatile memory device, whereinthe nonvolatile memory device comprises a physical nonvolatile memoryand a temporary memory, the method comprising: internally initializingthe nonvolatile memory device upon a start such that at least one writeoverlay window for an address space of the physical nonvolatile memoryis open after initialization, wherein the at least one write overlaywindow is configured to implement a status and command interface for ahost; and receiving one or more commands via the at least one writeoverlay window.
 11. The method of claim 10, further comprising openingall write overlay windows upon initialization.
 12. The method of claim11, further comprising closing one or more write overlay windows inresponse to a command received via the at least one write overlaywindow.
 13. The method of claim 10, wherein internally initializingfurther comprises: for a first address space within an address space ofthe physical nonvolatile memory, permitting a direct read operation fromthe physical nonvolatile memory and opening a second write overlaywindow for a write operation; and for a second address space within theaddress space of the physical nonvolatile memory, the second addressspace being different from the first address space, opening a first readoverlay window for a read operation and opening a third write overlaywindow for a write operation.
 14. The method of claim 10, furthercomprising: receiving information in an open write overlay window;storing the information in a temporary memory; and writing theinformation to the physical nonvolatile memory.
 15. A system comprising:a processing element configured to issue at least one of a readoperation, a write operation, a status request, or a command; a memorydevice comprising: a physical nonvolatile memory; and and a controllerconfigured to open at least one write overlay window upon initializationfor an address space of the physical nonvolatile memory such that the atleast one write overlay window implements a status and command interfacefor the processing element; and a bus configured to carry informationassociated with the at least one of the read operation, the writeoperation, the status request, or the command.
 16. The system of claim15, wherein the controller is configured to open all write overlaywindows of the memory device upon initialization.
 17. The system ofclaim 16, wherein the controller is configured to close one or morewrite overlay windows in response to a command received from theprocessing element via the at least one write overlay window and thebus.
 18. The system of claim 15: wherein for a first address spacewithin the address space of the physical nonvolatile memory, thecontroller is further configured to permit a direct read operation fromthe physical nonvolatile memory and to open a second write overlaywindow for a write operation upon initialization; and wherein for asecond address space within the address space of the physicalnonvolatile memory, the second address space being different from thefirst address space, the controller is further configured to open afirst read overlay window for a read operation and to open a third writeoverlay window for a write operation upon initialization.
 19. The systemof claim 15, wherein the controller is configured to receive informationin an open write overlay window, store the information in a temporarymemory, and write the information to the physical nonvolatile memory.20. The system of claim 15, wherein the controller is further configuredto open at least one read overlay window upon initialization, whereinthe at least one read overlay window is configured to provide at leastcommand response data.